Add index generation system that uses offsets into the WACZ itself. #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This is a pretty ingenious idea! |
|
The CI errors don't seem to be related to my patch? Not sure what to do about that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposed new
py-waczcommand allows you to generate a CDXJ file where the filenames and offsets refer to the WACZ itself rather than the WARC files within.The idea is that we should be able to store the WACZ files directly without unpacking them, and use this modified CDXJ data to ingest into OutbackCDX. This should mean we can play back WACZ files as easily as we can WARCs.
Currently DRAFT:
Because it needs a way to override the path prefix, and possibly even the actual WACZ name, depending on the use case.